home *** CD-ROM | disk | FTP | other *** search
- Path: news.primenet.com!bwilmes
- From: Bob Wilmes <bwilmes@primenet.com>
- Newsgroups: comp.object,comp.lang.c++
- Subject: Re: OO Vocabulary complaints.
- Followup-To: comp.object,comp.lang.c++
- Date: 26 Jan 1996 21:54:01 -0700
- Organization: Primenet (602)395-1010
- Sender: root@primenet.com
- Message-ID: <4ecb59$bo9@nnrp1.news.primenet.com>
- References: <4der2t$s1q@netlab.cs.rpi.edu> <4dhddu$aig@netlab.cs.rpi.edu> <RMARTIN.96Jan25095514@rcm.oma.com>
- X-Posted-By: bwilmes@usr2.primenet.com
-
- Compared to the hey-day of the artificial intelligence/expert systems
- work in the late 1980's, the development of codified methods and
- especially the work of the "Pattern" technologists makes me feel the
- scholarship of the OO community has come an extremely long way.
-
- Certainly Drs. Gamma, Johnson, Vlissides and Helm have shown us real
- ways to use a higher level of abstraction in real world situations,
- which is the hallmark of a powerful technique.
-
- The hardware community has made huge advances with tools such as VHDL
- and ASICs. Perhaps software will achieve the same capabilities within
- this decade.
-
-
- Robert C. Martin <rmartin@oma.com> wrote:
-
- : > Sadly, discussions of containers and iostreams tend to be stratosphereic,
- : > with little regard to how to actually use them and why. I think one
- : > reason for this is the use of terminology such as "iterator", "container",
- : > subclass, instance, message/procedure/function. Not to mention
- : > encapsulation, polymorphism, loose-coupling, instantiation, etc - all
- : > this makes things unneccessarily hard to understand, IMHO, and adds to
- : > the perception that all this OOPS stuff is a bunch of hooey.
-
- : In article <4e0ans$4gc@netlab.cs.rpi.edu> kanze@gabi.gabi-soft.fr (J. Kanze) writes:
-
- : I disagree strongly. I find that the use of such terms makes the
- : underlying concepts significantly easier to understand and discuss.
-
- : A good example is the Design Patterns book. In practice, hardly any of
- : the design patterns the authors present were new to me. *BUT* they
- : named them. They presented them as a standard pattern with a standard
- : name. Suddenly, I can explain my code to others, and have them
- : understand what I am doing. I have acquired an ability to talk about
- : something in a meaningful way.
-
- : Although this book has had a minimal effect on the actual code I'm
- : writing, it has completely changed my design documentation and the
- : comments. And, IMHO, that ain't nothing. I think it one of the most
- : important books that has recently appeared.
-
- : I strongly concurr with James. One of the ways that technologies
- : advance is by identifying and then naming concepts. Yes, this creates
- : a burden upon practitioners to learn the ever changing, ever growing
- : vocabularies. Some practitioners will complain that the new
- : vocabulary makes things unessesarily difficult to understand. But
- : their complaint should be rephrased as: "Damn I wish I didn't have to
- : work to keep current.".
-
-
- : --
- : Robert Martin | Design Consulting | Training courses offered:
- : Object Mentor Assoc.| rmartin@oma.com | OOA/D, C++, Advanced OO
- : 14619 N. Somerset Cr| Tel: (847) 918-1004 | Mgt. Overview of OOT
- : Green Oaks IL 60048 | Fax: (847) 918-1023 | Development Contracts.
-
-
- --
- ------------------------------------------------------------------------
- = Bob Wilmes = bwilmes@primenet.com = Phoenix/Scottsdale, Arizona, USA =
- ------------------------------------------------------------------------
-